HAL NAND Callbacks functions migration ¶

This section provides information about the HAL NAND function migration.

Registers NAND user callback. ¶

HAL1	HAL2
HAL_NAND_RegisterCallback()	Removed. In HAL1, the register callback APIs are dedicated to status memory notification callbacks (rising, falling, and high-level on the Ready/Busy signal). In HAL2, these callbacks are removed because memory status reads are handled internally by the process APIs. Consequently, the register callback APIs in HAL2 are therefore reserved only for series that support interrupt sources other than rising, falling, and high-level on the Ready/Busy signal, otherwise, they are removed.

HAL1

HAL2

HAL_NAND_RegisterCallback()

                Removed.

In HAL1, the register callback APIs are dedicated to status memory notification callbacks (rising, falling, and high-level on the Ready/Busy signal).
In HAL2, these callbacks are removed because memory status reads are handled internally by the process APIs. Consequently, the register callback APIs in HAL2 are therefore reserved only for series that support interrupt sources other than rising,
falling, and high-level on the Ready/Busy signal, otherwise, they are removed.

Related concepts: Individual callback registration APIs replace global register and unregister functions

Unregisters NAND user callback. ¶

HAL1	HAL2
HAL_NAND_UnRegisterCallback()	Removed. In HAL1, the unregister callback APIs are dedicated to status memory notification callbacks (rising, falling, and high-level on the Ready/Busy signal). In HAL2, these callbacks are removed because memory status reads are handled internally by the process APIs. Consequently, the unregister callback APIs in HAL2 are therefore reserved only for series that support interrupt sources other than rising, falling, and high-level on the Ready/Busy signal, otherwise, they are removed.

HAL1

HAL2

HAL_NAND_UnRegisterCallback()

                Removed.

In HAL1, the unregister callback APIs are dedicated to status memory notification callbacks (rising, falling, and high-level on the Ready/Busy signal).
In HAL2, these callbacks are removed because memory status reads are handled internally by the process APIs. Consequently, the unregister callback APIs in HAL2 are therefore reserved only for series that support interrupt sources other than rising,
falling, and high-level on the Ready/Busy signal, otherwise, they are removed.

Related concepts: Individual callback registration APIs replace global register and unregister functions

Callback for NAND interrupt. ¶

HAL1	HAL2
HAL_NAND_ITCallback()	In HAL1, the IT callback APIs is dedicated to status memory notification callbacks (rising, falling, and high-level on the Ready/Busy signal). In HAL2, this callback is removed since this status notification callback is now handled internally by the process APIs.

HAL1

HAL2

HAL_NAND_ITCallback()

                In HAL1, the IT callback APIs is dedicated to status memory notification callbacks (rising, falling, and high-level on the Ready/Busy signal).
In HAL2, this callback is removed since this status notification callback is now handled internally by the process APIs.